3 Plug-ins

Fragmalyzer plug-ins add features to the Fragmalyzer; they can add menu commande, provide additional AppleScript support, or enable the Fragmalyzer to work with a binary format. Plug-ins are stored in the "Plug-ins" folder, which resides in the same folder as the Fragmalyzer application. There can be additional folders within the main plug-ins folder; any sub-folder whose name is surrounded by parentheses (e.g. "(disabled plugins)") will not be searched for plug-ins.

To disable a plug-in, you can:

• Trash the plug-in, or
• Move it out of the "Plug-in" folder hierarchy, or
• Move it into an unsearched sub-folder (named e.g. "(disabled plugins)")

The following plug-ins are included in the Fragmalyzer package:

PEF Support

A binary format plug-in that provides support for working with PEF-based fragments. PEF is the standard format used by the Code Fragment Manager (Mac OS 7-9). You should not remove or disable this plug-in.

Save Fragments

Adds the "Save as..." command to the File menu, and corresponding AppleScript support. It saves the selection in a single file. It can save the selection in any of the following ways:

• as fragments
• as stub libraries
• as weak-linking stub libraries
• as non-linking stub libraries
• as native resources (not accelerated)
• as a list of exported symbols (.exp file)
• as a list of imported symbols (.imp file) creates a stub library

If export symbols are selected, then only those symbols will be included when creating a stub library or .exp file.
Note: This plug-in replaces the "Save as Stub Library" plug-in.

Set Stack Size

Adds the "Set Stack Size" submenu to the Fragmalyze menu, and corresponding AppleScript support. When you have an application fragment selected, you can use this command to modify the stack size for the application as specified in the application's "cfrg" resource.
Note: You must have write-access to the application file, and you cannot modify the stack size of a running application.

Set Library Folder

Adds the "Set Library Folder..." command to the Fragmalyze menu, and corresponding AppleScript support. This command sets the folder that the Code Fragment Manager will search to locate application libraries (in addition to the usual places: the extensions folder and the application folder). This is really only useful if you specify a folder on the same volume as your application, usually a subfolder of the application folder; otherwise the alias will be broken when the application folder is moved to another machine/volume.
Note: You must have write-access to the application file, and you cannot modify the library folder of a running application.

Set Link Strength

Adds the "Strengthen Link"/"Weaken Link" commands to the Fragmalyze and Symbol menus. Select one library at a time or one or more symbols. If you select more than one symbol that do not all have the same link-strength, this will change the first symbol's link strength and change all other selected symbols to match.
Note: You must have write-access the fragment, and you cannot modify the links in a running process.

PowerPC Code Browser

Adds "Browse Code" to the Fragmalyze menu, "View Code" to the Symbol menu, and adds the "Code" menu.

• Double-clicking on an exported symbol will open a code browser window at that symbol
• "Browse Code" will open the code browser to the main entrypoint (if the fragment has one)
• Hyperlink-style navigation: click on symbol names in the disassembly to jump to that symbol. "Go Back" command returns to the previous location.
• Live-scrolling: both the symbol list and the disassembly view update instantly as you move the scrollbar thumbs.
• Symbol filtering: allows you to limit the symbols shown to those with a particular prefix (e.g. all functions that start with "Debug..."). Filtering ignores extra leading underscores.
• The symbol list is built from embedded traceback tables (if present), the set of exported functions, the initialization, termination, and main entrypoints, and all glue code, with "anonymous" symbols for everything else.
• You can browse code in memory, on disk, even in accelerated, native, and fat code resources!

More About the PowerPC Code Browser (This link does not work in Netscape Navigator... sorry!)

Section Browser

Adds "View Section" sub-menu to the Fragmalyze menu. You can browse any of the three sections of the fragment (fine print: not all fragments have both code and data; some may even have more than three sections -- these will be browsable in a future version of the plug-in). The browser show the contents (unpacked) as hexadecimal and as text. Sections with relocations (e.g. most data sections) will display the relocations by way of special formatting:

• Italic values with a light red background are imported symbols (at run-time they would point to the function transition vectors or data)
• Plain values with a light green background are offsets within the same section
• Blue underlined text with a light yellow background are offsets within the code section

Window Menu

Adds a "Window" menu to the menu bar. The new commands should be familiar.

You can get additional plug-ins (as they become available) from the Fragmalyzer home page. To use them, just download the plug-ins and copy or move them to your plug-ins folder. You can also put aliases to plug-ins in the plug-ins folder.

You can write your own plug-ins to extend the functionality of the Fragmalyzer. You can view the Quick Reference to Writing Plug-ins at the Fragmalyzer web site.

Download plug-ins
Writing plug-ins

Previous | Back to Contents    © 1998-2000 Dan Wright, All rights reserved.